Description

Remove broken MV3 reports. These reports relied upon data from the mv3-perf-stats E2E test job, which itself relied upon the user-data-dir chromedriver setting removed in #24696. They have been broken since that PR.

These reports were very useful in prioritizing MV3 work at the time, but we haven't needed them recently.

The mv3-stats E2E test suite has also been removed (this is an older version of mv3-perf-stats that has been unused for even longer), along with the charts that were used for this report.

Related issues

Relates to #28572

Manual testing steps

Check that the metamaskbot comment no longer has the links to these broken reports. They look like this:

• mv3: Background Module Init Stats
• mv3: UI Init Stats
• mv3: Module Load Stats

Screenshots/Recordings

N/A

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Extension Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.